Architecture Decision within Value-Based Software Engineering concepts

Architectures in software intensive systems are a significant field of study while it is representing static structure, dataflow, and relationships among subsystems or components. Also, architectures could be considered an artifact as blueprint of software system to make sure that design approach will yield an acceptable system in early system analysis. As the complexity of system increases, there will be several approaches to design or select components to improve qualities, namely performance, modification, and security, and there are many stakeholders involved in those architectural concerns such as implementors, testers, maintainers, and managers. To select right and workable architectural approaches, architects firstly need to recognize the values among stakeholders, how to affect them, and how to lead negotiated architectural decisions against the value-neutral approach that focuses on only technical issues. In this paper, we primarily propose a method that systematically derives architectural decision framework to reflect both economical and technical issues in context of architecture processes.